Transaction allocation

ABSTRACT

Systems and methods of allocating transactions among business objects are described. Allocation is accomplished using a multi-phase process. In a first phase, allocation of the transactions among a set of business objects is attempted. In a subsequent phase, allocation of transactions that were either unallocated, under-allocated, or over-allocated in the first phase is determined. The second phase includes using a set of allocation rules to identify business objects configured to manually determine allocation of the unallocated, under-allocated, or over-allocated transactions. The invention is applicable to a variety of business objects including people, organizations, accounts, tasks, or the like.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent applicationSer. No. 10/426,474, entitled “Hierarchical Transaction Filtering” andfiled on Apr. 29, 2003.

BACKGROUND

1. Field of the Invention

The invention is in the field of computer science and more specificallyin the field of transaction management.

2. Description of the Prior Art

In a typical organization, sale of a product or service can impactmultiple parties. For example, in a business environment suchtransactions may involve a sales team, their supervisors, theirsupporters and post sale personnel. In some cases it is desirable todistribute credit (e.g., commissions) for a sale or responsibility for apurchase, among these parties.

Available software includes applications configured to track sales anddistribute commissions to personnel within an organization. In theseapplications different personnel are assigned various allocationcriteria for use in determining the transactions for which they shouldreceive credit. For example, a sale may be associated with a specificsales territory, a specific product type, a sales team, an individualsalesperson, a channel partner, a price range, a payment schedule, etc.Each of these characteristics may be associated with allocation criteriaand used to determine one or more individuals who should receive creditfor the sale.

In a typical prior art application, each transaction is individuallyexamined and its characteristics are compared with each person'sallocation criteria. When the characteristics match the criteria, theperson receives some credit for the transaction. In large organizations,these comparisons may include thousands of transactions and hundreds ofpersonnel. The total number of comparisons is, therefore, large.

Previously available systems have a number of drawbacks. For example,since each transaction is individually examined, the performance ofthese systems responds poorly to increases in transaction volume. Inaddition, setup and maintenance of prior art systems are difficult sinceeach person's allocation criteria is manually defined. Likewise, changesin products, personnel or organization structure can require, possiblyextensive, modification of system data. For example, when a new productis introduced the allocation criteria relating to each person who mayreceive credit for a sale of the product may need to be modified beforean appropriate credit can be assigned. Finally, in existing systems, theways in which credits are assigned can be unclear to personnel trackingor expecting to receive commissions. These systems often do not lendthemselves well to the generation of reports that itemize thecommissions due to each person.

There is a need for systems and methods to more efficiently manageallocation of transactions, such as sales commissions. For example,there would be a benefit to having systems capable of processing largenumbers of transactions more efficiently, automating aspects ofallocation criteria management, or more clearly showing to a salesperson how their commission was calculated.

Many systems and methods of allocating transactions include a problem oftransactions that are unallocated, under-allocated, or over-allocated.For example, in some cases a sales transaction fails to meet theallocation criteria of any person to whom commission might be paid. Insome cases, a sales transaction meets the allocation criteria of somepeople but not enough people to completely allocate the availablecommission. The existing art does not include efficient methods forallocating transactions that are unallocated, under-allocated orover-allocated.

SUMMARY OF THE INVENTION

Embodiments of the invention include systems and methods of allocatingtransactions among a number of business objects. These business objectsinclude, for example, individuals and/or organizations. The transactionstypically involve payment of funds, such as sales commissions, but mayalso include allocation of inventory, movement of goods, or the like, asdiscussed further herein. Allocation is accomplished using predefinedrules stored in a hierarchical data structure that is based onrelationships between the business objects. The predefined rules andhierarchical data structure are used to form generated allocation rulesassociated with the business objects. The generated allocation rulesare, in turn, used for allocating the transactions among the businessobjects. Each of the allocated transactions includes characteristicsthat can be determined to satisfy or not to satisfy a generatedallocation rule. For example, in some embodiments, the business objectsinclude individuals and groups within a company, the hierarchical datastructure is based on the company organization and the generatedallocation rules are used to determine sales commissions earned by eachbusiness object.

Various embodiments of the invention include transaction filteringsystem for allocating transactions among a plurality of businessobjects, the system comprising storage configured to store generatedallocation rules and to store transaction data associated with theplurality of transactions, each generated allocation rule beingassociated with at least one of the plurality of business objects andbeing generated using relationships between members of the plurality ofbusiness objects, and a query engine configured to query the transactiondata using the generated allocation rules.

Various embodiments of the invention include a hierarchical datastructure comprising a root node, one or more intermediate nodes relatedto the root node, one or more predefined rules, each predefined ruleassociated with a member of the one or more intermediate nodes, a leafnode, and a generated allocation rule associated with the leaf node andconfigured for use in determining allocation of transactions to abusiness object associated with the leaf node, the generated allocationrule including a member of the one or more predefined rules inheritedfrom the one or more intermediate nodes.

Various embodiments of the invention include a computing system forhierarchical transaction filtering, the computing system comprisingstorage configured to store a hierarchical data structure, a generatedallocation rule, and transaction data, a rule generation engineconfigured to produce the generated allocation rule using data stored inthe hierarchical data structure, and a query engine configured to querythe transaction data using the generated allocation rule.

Various embodiments of the invention include a transaction allocationoutput comprising a set of transactions selected using a query, thequery based on a generated allocation rule generated using ahierarchical data structure and associated with a leaf of thehierarchical data structure, at least two transactions of the set oftransactions including a transaction value, and a summation of thetransaction values.

Various embodiments of the invention include a method of producing agenerated allocation rule, the method comprising accessing a datastructure including a root node, an intermediate node and a leaf node,reading the root node of the data structure, adding any predefined ruleassociated with the root node to the generated allocation rule,traversing the data structure to the intermediate node, reading theintermediate node, adding any predefined rule associated with theintermediate node to the generated allocation rule, traversing the datastructure to the leaf node, adding any predefined rule associated withthe leaf node to the generated allocation rule, and storing thegenerated allocation rule.

Various embodiments of the invention include a method of producing aplurality of generated allocation rules, the method comprising accessinga hierarchical data structure including a plurality of nodes, andtraversing the plurality of nodes, at each node traversed, reading thetraversed node, combining any predefined rule associated with thetraversed node with any of the plurality of generated allocation rulesinherited from a parent node, to produce another of the plurality ofgenerated allocation rules, associating the another of the plurality ofgenerated allocation rules with the traversed node, storing the anotherof the plurality of generated allocation rules, and determining if allleaf nodes have been traversed.

Various embodiments of the invention include a method of determiningallocation of a plurality of transactions, the method comprisingreceiving first transaction data characterizing a first member of theplurality of transactions, receiving second transaction datacharacterizing a second member of the plurality of transactions, storingthe first and second received transaction data, accessing a plurality ofgenerated allocation rules, each of the plurality of generatedallocation rules being associated with one of a plurality of businessobjects represented by an hierarchical data structure, executing aplurality of queries on the stored transaction data using a queryengine, each of the plurality of queries being based on one of theplurality of generated allocation rules, and storing results of theexecuted queries.

Various embodiments of the invention include a method of generating atransaction allocation output, the method comprising receiving a queryresult including one or more transactions, the query result generatedusing a query, the query generated using a hierarchical data structureand the query associated with a leaf node of the hierarchical datastructure, the query applied to a set of transactions, parsing each ofthe one or more transactions to determine a value of each of the one ormore transactions, summing the values determined by parsing each of theone or more transactions, and including the sum of the determined valuesin the transaction allocation output.

Various embodiments of the invention include a system for determiningallocation of a plurality of transactions among a plurality of businessobjects, the system comprising storage configured for storingtransaction data characterizing the plurality of transactions, means forproducing a plurality of generated allocation rules, using relationshipsbetween nodes of a data structure, means for executing a plurality ofqueries on the stored transaction data, using the plurality of generatedallocation rules.

Various embodiments of the invention include a computer readable mediumstoring computer code for producing a generated allocation rule, thecomputer code comprising a code segment for accessing a data structureincluding a root node, an intermediate node and a leaf node, a codesegment for reading the root node of the data structure, a code segmentfor adding any predefined rule associated with the root node to thegenerated allocation rule, a code segment for traversing the datastructure to the intermediate node, a code segment for reading theintermediate node, a code segment for adding any predefined ruleassociated with the intermediate node to the generated allocation rule,a code segment for traversing the data structure to the leaf node, acode segment for adding any predefined rule associated with the leafnode to the generated allocation rule, and a code segment for storingthe generated allocation rule.

Various embodiments of the invention include a method of producing agenerated allocation rule, the method comprising accessing a datastructure including a root node, an intermediate node and a leaf node,reading the root node of the data structure, adding any predefined ruleassociated with the root node to the generated allocation rule,traversing the data structure to the intermediate node, reading theintermediate node, adding any predefined rule associated with theintermediate node to the generated allocation rule, traversing the datastructure from the intermediate node, reading the leaf node, adding anypredefined rule associated with the leaf node to the generatedallocation rule, and storing the generated allocation rule. In some ofthese embodiments, traversing the data structure from the intermediatenode includes traversing the data structure to the leaf node. In some ofthese embodiments, traversing the data structure from the intermediatenode includes traversing the data structure to the root node.

Various embodiments of the invention include a transaction filteringsystem for allocating transactions among a plurality of businessobjects, the system comprising storage configured to store generatedallocation rules and to store transaction data associated with theplurality of transactions, each generated allocation rule beingassociated with at least one of the plurality of business objects andbeing generated using relationships between members of the plurality ofbusiness objects, a query engine configured to query the transactiondata using the generated allocation rules, and an allocation managerconfigured to make one or more attempts to allocate a member of theplurality of transactions among the plurality of business objects.

Various embodiments of the invention include a hierarchical datastructure comprising a root node, one or more intermediate nodes relatedto the root node, a leaf node, and a first generated allocation ruleassociated with the leaf node and configured for use in determiningallocation of transactions to a business object associated with the leafnode, a second generated allocation rule associated with one of the oneor more intermediate nodes and configured for use in determining abusiness object configured to manually determine the allocation of oneof the transactions to a business object.

Various embodiments of the invention include a computing system forhierarchical transaction filtering, the computing system comprisingstorage configured to store a hierarchical data structure, a firstgenerated allocation rule, a second generated allocation rule, andtransaction data, an allocation manager configured to track allocationof transactions represented by the transaction data, and a query engineconfigured to execute a first query on the transaction data using thefirst generated allocation rule and, responsive to the first query, toexecute a second query on the transaction data using the secondgenerated allocation rule.

Various embodiments of the invention include a transaction allocationoutput comprising a first set of transactions selected using a firstquery, the first query based on an allocation rule generated using ahierarchical data structure and associated with a leaf node of thehierarchical data structure, at least one transaction of the first setof transactions including a transaction value, a second set oftransactions whose allocation is determined by a business object, thebusiness object being identified using a second query, at least onetransaction of the second set of transactions including a transactionvalue, and a summation of the transaction values.

Various embodiments of the invention include a method of determiningallocation of one or more transactions, the method comprising accessinga first allocation rule associated with one of a plurality of businessobjects represented by a hierarchical data structure, executing a firstquery on transaction data using a query engine, the first query beingbased on the first allocation rule, the transaction data characterizingthe one or more transactions, accessing a second allocation ruleassociated with another of the plurality of business objects representedby the hierarchical data structure, and executing a second query on asubset of the transaction data using the query engine, the second querybeing based on the second allocation rule and identifying a businessobject for determining allocation of at least one of the one or moretransactions.

Various embodiments of the invention include a method of generating atransaction allocation output, the method comprising receiving a queryresult including one or more transactions, the query result generatedusing a query applied to a set of transactions, the query generatedusing a hierarchical data structure and the query associated with a leafnode of the hierarchical data structure, determining transactionallocation of any of the one or more transactions that are unallocated,under-allocated, or over-allocated, parsing each of the one or moretransactions to determine a value of each of the one or moretransactions, summing the values determined by parsing each of the oneor more transactions, and including the sum of the determined values inthe transaction allocation output.

Various embodiments of the invention include a system for determiningallocation of a plurality of transactions among a plurality of businessobjects, the system comprising, storage configured for storingtransaction data characterizing the plurality of transactions, means forexecuting a plurality of queries on the stored transaction data, using aplurality of allocation rules, the queries configured to determineallocation of the plurality of transactions, and means for manuallydetermining allocation of a subset of the plurality of transactions, thesubset including unallocated, under-allocated or over-allocatedtransactions.

Various embodiments of the invention include a computer readable mediumstoring computer code for determining an allocation plan, the computercode comprising a code segment for accessing a first allocation ruleassociated with one of a plurality of business objects represented by ahierarchical data structure, a code segment for executing a first queryon transaction data using a query engine, the first query being based onthe first allocation rule, the transaction data characterizing the oneor more transactions, a code segment for accessing a second allocationrule associated with another of the plurality of business objectsrepresented by the hierarchical data structure, and a code segment forexecuting a second query on a subset of the transaction data using thequery engine, the second query being based on the second allocation ruleand identifying a business object for determining allocation of at leastone of the one or more transactions.

BRIEF DESCRIPTION OF THE VARIOUS VIEWS OF THE DRAWING

FIG. 1 illustrates a hierarchical transaction filtering system accordingto various embodiments of the invention;

FIG. 2 illustrates hierarchical relationships between a set of businessobjects according to various embodiments of the invention;

FIG. 3 illustrates a method of determining a generated allocation ruleaccording to various embodiments of the invention;

FIG. 4 illustrates an alternative method of determining a generatedallocation rule according to various embodiments of the invention;

FIG. 5 illustrates a method of allocating a plurality of transactionsaccording to various embodiments of the invention; and

FIG. 6 illustrates a method of generating a transaction allocationoutput according to various embodiment of the invention;

FIG. 7 illustrates a hierarchical data structure according to variousembodiments of the invention; and

FIG. 8 illustrates a method of allocating transactions according tovarious embodiments of the invention.

DISCLOSURE OF THE INVENTION

Embodiments of the invention include systems and methods of generatingallocation rules and using these generated allocation rules to allocatetransactions, such as payment of sales commissions, among members of anorganization. Each of these members are represented by a node in ahierarchical data structure and are optionally associated with somepredefined rule (e.g., allocation criteria). Generated allocation rules,used for performing an allocation, are produced using the predefinedrule and associations implied by the hierarchical data structure. Forexample, in some embodiments, each node in the hierarchical datastructure is associated with a generated allocation rule produced bycombining any associated predefined rule with a generated allocationrule inherited from a parent node. Through this process of inheritanceand combination, a generated allocation rule is determined for each nodein the hierarchical data structure. These generated allocation rules arethen used to select transactions to be allocated to the membersassociated with the nodes of the hierarchical data structure.

In a typical embodiment, each member of an organization is treated as abusiness object associated with a node in the hierarchical datastructure. Generated allocation rules, associated with the node and thebusiness object, are derived through a process that includes combiningany predefined rule characterizing the business object with anyallocation rule (e.g., generated allocation rule) inherited from aparent node. Through inheritance of allocation rules, each node (otherthan a root node) is associated with a generated allocation rule that isan aggregation of the predefined rule associated with its parent nodes,and grandparent nodes, etcetera, in the hierarchical data structure.Generated allocation rules are produced as the hierarchical datastructure is developed or by traversing the hierarchical data structurein an orderly manner. When a business object is not characterized by anypredefined rule, the generated allocation rule associated with thebusiness object, and corresponding node, is determined by inheritancefrom a parent node.

In a typical method of the invention, sales data are received and storedin a database as transactions to be allocated. In order to allocatethese transactions among business objects, the database is queried usingqueries based on the generated allocation rules. Each query is used toselect those transactions that satisfy the predefined rules included ina particular generated allocation rule and the selected transactions areallocated to a business object associated with that generated allocationrule. Thus, a particular person is allocated transactions whosecharacteristics match the generated allocation rule associated with thatperson, and the allocated transactions are selected using a query basedon the associated generated allocation rule. Using this approach, alarge number of transactions can be allocated using a small number ofqueries, because the number of queries is responsive to the number ofbusiness objects not the number of transactions. When the number oftransactions significantly outnumbers the number of business objects,this approach is typically more efficient than individually comparingeach transaction with a set of allocation rules.

In various embodiments, business objects include individual persons,groups, organizations, corporations, geographic locations, projects,products, production resources, tasks, or the like. In theseembodiments, transactions optionally include sales, sales commissions,purchases, purchase costs, inventory allocation, allocation of financialresources, allocation of capital resources, tasks, steps in a process,compensation, quality control, billing, or the like. For example, in oneembodiment the business object is a task and the transaction is aninventory allocation to that task. In another embodiment, the businessobject is a person and the transaction is a task (e.g., a sales call)that can be assigned to a person. In another embodiment the businessobject is a shipping resource (e.g., a cargo carrier) and thetransaction is a transportation task. In some embodiments, thetransactions include sales and associated sales commissions, and thebusiness objects include members of a sales team and associated parties.For the purposes of example, these embodiments will be discussed furtherherein. However, the methods and systems discussed in relation to theseembodiments are readily applied to alternative embodiments of theinvention including other types of business objects and transactions,without going beyond the intended scope of the invention.

In many businesses, sales are achieved as the result of a team effortinvolving sales personnel, marketing personnel, channel partners, salesengineers and managers. When a sale occurs, a commission or other creditis to be allocated among the parties who contributed to the sale.Typically, each party (e.g., business object) is associated with agenerated allocation rule or set of generated allocation rules thatdetermine if the party is entitled to an allocation from a particularsale. Each sale (e.g., transaction) is characterized by attributes thatcan be compared with the generated allocation rules. For example, aparticular sales person may be associated with a generated allocationrule that specifies allocation of 2% of sales revenue within aparticular geographic region, 1% of sales from a particular productline, 2% of sales to a particular customer, and 0.5% of sales by othermembers of her sales team. In this example, a transaction may becharacterized by a geographic location, a product, a customer and asales team. A wide variety of such allocation schemes are known in theart. In the invention, these schemes are expressed as generatedallocation rules derived from a hierarchical data structure. Eachcondition, such as “2% of sales to a particular customer,” is considereda predefined rule.

FIG. 1 illustrates a Transaction Filtering System 100 according tovarious embodiments of the invention. Transaction Filtering System 100includes a Computing System 110 optionally accessible through a Client120 and configured to receive transactions from a Transaction Source130. Computing System 110 may be a single computing device or a set ofinterconnected computing devices. The set of interconnected computingdevices optionally includes both local and remote devices. In typicalembodiments, Client 120 includes a computing device such as a computer,personal digital assistant, network access device, or the like. Client120 optionally accesses Computing System 110 though a network such asthe Internet, local area network, wide area network, or the like. Insome embodiments, Computing System 110 is accessed through a browsersupported by Client 120.

Transaction Source 130 is a source of transactions to be allocated. Forexample, in various embodiments, Transaction Source 130 is apoint-of-sale system, an accounting system, a sales reporting system, aninventory system, a task management system, or the like. TransactionSource 130 is optionally supported by elements of Computing System 110.For example, in some embodiments, Transaction Source 130 includes asales accounting program executing on Computing System 110.

Computing System 110 includes Storage 140 configured to store dataassociated with systems and methods of the invention. For example,Storage 140 is typically configured to store Organizational Data 145,Rule Data 150 and Transaction Data 155. Organizational Data 145 includesa hierarchical data structure configured to store relationships betweenbusiness objects. An example of Organizational Data 145 is illustratedby FIG. 2 as discussed further herein. Rule Data 150 includes generatedallocation rules associated with business objects characterized byinformation within Organizational Data 145. These generated allocationrules are produced using a Rule Generation Engine 160. The generationprocess is further described with reference to FIGS. 3 and 4.Transaction Data 155 includes transactions received from TransactionSource 130. In a typical embodiment, a plurality of transactions arestored in Transaction Data 155.

A Query Engine 170 is configured to execute queries based on Rule Data150. In a typical embodiment, each generated allocation rule within RuleData 150 is processed to place the generated allocation rule in astructured query language (SQL) format. In some embodiments, thegenerated allocation rules are stored in Rule Data 150 as SQL queriesand can be used by Query Engine 170 without modification. The generatedallocation rule based queries are used to select transactions stored inTransaction Data 155.

Results of queries executed using Query Engine 170 are passed through anOutput Interface 180 to generate a transaction allocation output that isoptionally accessible to Client 120. Output Interface 180 is optionallyconfigured to format the results in a report format including data suchas a summation of selected transaction values. In some embodiments, thetransaction allocation output is generated in a meta-language formatsuch as HTML, or the like.

Query Engine 170 and optionally Output Interface 180 are responsive toan Allocation Manager 190. Allocation Manager 190 includes computer codeconfigured to manage and optionally coordinate the functions carried outby other aspects of Computing System 110. For example, in someembodiments, Allocation Manager 190 keeps track of the progress made inallocating a set of transactions according to an allocation plan. Anallocation plan is a plan for allocating transactions to/among a set ofbusiness objects. In some embodiments, Allocation Manager 190 isconfigured to make several attempts to allocate a particulartransaction. In some embodiments, Allocation Manager 190 tracksunallocated transactions, under-allocated transactions, and/orover-allocated transactions.

FIG. 2 illustrates a Hierarchical Data Structure, generally designated200, according to some embodiments of the invention. In theseembodiments, Hierarchical Data Structure 200 is included inOrganizational Data 145 (FIG. 1) and is used to store relationshipsbetween a set of Business Objects, 210A-210W. Business Objects 210A-210Winclude geographic regions (210A-210F), sales channel types (210G-210H),product types (210I-210J), individual sales people (210K-210W), or thelike. In this example, Business Object 210A is represented by a rootnode of Hierarchical Data Structure 200. Business Objects 210B-210J and210P are represented by intermediate nodes and Business Objects210K-210N and 210Q-210W are represented by leaf nodes.

In some embodiments, an individual sales person is optionally associatedwith more than one Business Object 210. For example, a sales person maybe involved with both direct sales in the west and hardware sales inOhio, and thus be both Business Objects 210K and 210T. A sales person isalso optionally represented by an intermediate node such as BusinessObject 210P. The relationships between Business Object 210P(intermediate node) and Business Objects 210Q-210S (leaf nodes) may, forexample, be that of sales group leader and sales group members. Some ofBusiness Objects 210A-210W are optionally representative of differentorganizations (e.g., companies, divisions, or groups). For example,Business Objects 210M-210S may be representative of a separate channelpartner company.

In a typical embodiment, each of Business Objects 210A-210W isassociated with at least one generated allocation rule. These generatedallocation rules are produced by Rule Generation Engine 160 (FIG. 1)using an inherited allocation rule and any predefined rulecharacterizing a particular member of Business Objects 210A-210W. Forexample, Business Object 210B inherits a generated allocation rule fromBusiness Object 210A. In the illustrated example this generatedallocation rule may be “a sale within the United States territory.” Inaddition, Business Object 210B is characterized by a predefined rule “asale within the West territory.” The generated allocation ruleassociated with Business Object 210B may, therefore, be the combinationof the inherited rule and the predefined rule, resulting in a generatedallocation rule of “a sale within the United States territory and a salewithin the West territory.” Likewise, generated allocation rules forBusiness Objects 210G and 210H may be “a sale within the United Statesterritory, a sale within the West territory and a direct sale” and “asale within the United States territory, a sale within the Westterritory and a channel partner sale,” respectively.

The embodiment of Hierarchical Relationship Structure 200 illustrated inFIG. 2 includes a single parent node for each node other than the rootnode (Business Object 210A). This structure simplifies inheritance ofgenerated allocation rules from each parent node to each daughter node.However, in alternative embodiments, any of Business Object 210B-210Wmay appear more than once in Organizational Data 145. In someembodiments, a particular Business Object 210 inherits generatedallocation rules from more than one parent node. The inheritanceapproach to production of generated allocation rules, as employed byRule Generation Engine 160, is possible as long as there are a finitenumber of paths between each node and the root node, (i.e., no circularpaths exist). Thus, while a hierarchical data structure is disclosed forillustrative purposes, embodiments of the invention include otherrelational data models accommodating the principle of inheritance. Insome embodiments, of the invention, not all nodes are associated with amember of Business Objects 210A-210W. For example, some data structures,such as a binary tree representation of Hierarchical Data Structure 200,include nodes used primarily for navigation. In some embodiments, onlyleaf nodes are associated with a member of Business Objects 210A-210Wand intermediate nodes are used for navigating the data structure. Evenwhen not associated with a member of Business Objects 210A-210W, a nodemay optionally be associated with a predefined allocation rule.

FIG. 3 illustrates a method of determining a generated allocation ruleaccording to various embodiments of the invention. In an optionalGenerate Hierarchical Data Structure Step 300, Organizational Data 145,such as that illustrated in FIG. 2 is generated and stored in Storage140. This step includes establishing hierarchical relationships betweenBusiness Objects 210A-210W and/or defining predefined rulescharacterizing Business Objects 210A-210W. This step may be avoided whenpreviously existing data is used. Generate Hierarchical Data StructureStep 300 is optionally an ongoing process wherein Organizational Data145 is updated by addition, deletion or other modification of BusinessObjects 210A-210W, over time.

In a Read Root Node Step 310, a root node of Hierarchical Data Structure200 (e.g., the node representing Business Object 210A) is accessed usingRule Generation Engine 160. From this node all the nodes withinOrganizational Data 145 are accessible. In some embodiments, this accessincludes passing a pointer referencing a memory location whereinBusiness Object 210A is stored, to Rule Generation Engine 160. Read RootNode Step 310 typically includes reading any predefined rulecharacterizing Business Object 210A.

In an Add Root Node Criteria Step 320, any predefined rulecharacterizing Business Object 210A is added to the allocation rulebeing generated. The result of this addition is a generated allocationrule, for the root node, and associated with Business Object 210A. Afterthis step, the generated allocation rule associated with Business Object210A may include only the predefined rule characterizing Business Object210A, or alternatively, may also include a default predefined ruleintroduced by Rule Generation Engine 160. This predefined rule mayinclude, for example, filtering criteria based on the characteristics ofthe transaction (such as sales amount), or characteristics of thebusiness object (such as product cost).

In a Traverse to Node Step 330, Hierarchical Data Structure 200 istraversed to another node representing one of Business Objects210B-210W. Traversal of Organizational Data 145 is typicallyaccomplished using one of the many algorithms known in the art fornavigating a data structure. Once Rule Generation Engine 160 traversesto a node within Organizational Data 145 that node is considered the“current” node upon which Rule Generation Engine 160 performsoperations. In Read Node Step 340, any predefined rule associated withthe current node is read by Rule Generation Engine 160.

In an Add Node Criteria Step 350 the read predefined rule is added toany generated allocation rule inherited from a parent node of thecurrent node. Typically, each node other than the root node has oneparent node from which a generated allocation rule is inherited. Thecombination of the inherited generated allocation rule and the readpredefined rule forms a generated allocation rule for the current nodeand any associated member of Business Objects 210B-210W. In alternativeembodiments, a node may inherit allocation rules from more than oneparent node. In these embodiments, the generated allocation rule for thecurrent node is the combination of all inherited allocation rules andany read predefined rules.

In a Store Allocation Rule Step 360, the generated allocation ruleassociated with the node is stored in Rule Data 150 (FIG. 1). Thestorage is optionally in a format accessible to Query Engine 170. Insome embodiments, Query Engine 170 is configured to generate a querybased on each of the stored rules and in other embodiments the rules arestored directly as formatted queries. In alternative embodiments, thegenerated allocation rules are stored in Rule Data 150 after each ruleis completed.

As determined in a Step 370, if there are further nodes, that have notbeen read using Read Node Step 340, then the method returns to Traverseto Node Step 330. This process is typically repeated until all nodeshave been visited.

FIG. 4 illustrates an alternative method of determining a generatedallocation rule according to various embodiments of the invention. Inthis embodiment, generated allocation rules are produced duringdevelopment of Hierarchical Data Structure 200. In a Define Root NodeStep 410, a root node associated with Business Object 210A is defined.This node serves as a root for Hierarchical Data Structure 200,including nodes associated with Business Objects 210A-210W. Define RootNode Step 410 optionally includes specification of a predefined rulecharacterizing Business Object 210A.

In an optional Define Root Node Allocation Rule Step 420, RuleGeneration Engine 160 is used to define a generated allocation ruleassociated with the root node. The generated allocation rule is producedby combining any default rule received from Rule Generation Engine 160with any predefined rule specified in Define Root Node Step 410.

In a Define Daughter Node Step 430, a daughter node, optionallyassociated with a member of Business Objects 210B-210W, is defined. Thedaughter node may be either an intermediate node or a leaf node. Thefirst time Define Daughter Node Step 430 is executed the defined nodewill be a daughter of the root node. In subsequent executions, thedefined node may be a daughter of either the root node or anintermediate node. Define Daughter Node Step 430 optionally includesspecification of a predefined rule characterizing a member of BusinessObjects 210B-210W associated with the defined daughter node.

In an Inherit Rule Step 440, the daughter node, defined in DefineDaughter Node Step 430, inherits a generated allocation rule from itsparent node. In alternative embodiments, the daughter node has more thanone parent node and optionally inherits a generated allocation rule fromeach parent node.

In a Modify Rule Step 450, the inherited allocation rule is modified byadding any predefined rule characterizing the member of Business Objects210B-210W associated with the defined daughter node. The result of thisaddition is a new generated allocation rule associated with the daughternode. Steps 430 through 450 are repeated as needed as new nodes andassociated Business Objects 210B-210W are added to Hierarchical DataStructure 200.

The methods illustrated in FIG. 3 and FIG. 4 are optionally both used inthe same embodiments of the invention. For example, in some embodiments,the method illustrated by FIG. 4 is used when Hierarchical DataStructure 200 is first developed and the method illustrated by FIG. 3 isused to update generated allocation rules if Hierarchical Data Structure200 has been modified. This modification optionally includes, forexample, addition or deletion of nodes, changes in predefined rules,changes in associations between nodes and/or Business Objects 210A-210W,or the like. In various embodiments, data generated in Define Root NodeStep 410 and Define Daughter Node Step 430 are stored in OrganizationalData 145 (FIG. 1), while data generated in Define Root Node AllocationRule Step 420 and Modify Rule Step 450 are stored in Rule Data 150.

FIG. 5 illustrates a method of allocating a plurality of transactionsaccording to various embodiments of the invention. In a ReceiveTransactions Step 510 transaction data characterizing transactions arereceived from Transaction Source 130 (FIG. 1). For example, in someembodiments, Transaction Source 130 includes records of sales entered byindividual sales personnel or their managers. In a Store TransactionsStep 520, the transactions received in Receive Transactions Step 510 arestored in Storage 140 as Transaction Data 155. In some embodiments, thisstorage is accomplished using an SQL compatible database. Typically, anumber of transactions are stored before completion of ReceiveTransactions Step 510 and Store Transactions Step 520. In someembodiments, because the number of queries made to allocate the storedtransactions is based upon the number of generated allocation rules usedfor allocating those transactions, rather than upon the number oftransactions, further benefit is achieved when the number oftransactions is greater than the number of generated allocation rules.

In an Access Rules Step 530, Query Engine 170 is used to access RuleData 150 and the generated allocation rules stored therein. The accessedgenerated allocation rules include those generated allocation rulesproduced using Organizational Data 145 and Rule Generation Engine 160.In an Execute Queries Step 540, Query Engine 170 is used to performqueries on the transactions received in Receive Transactions Step 510.These queries are based on the generated allocation rules accessed inAccess Rules Step 530. In some embodiments, the generated allocationrules are retrieved in a query format, such as SQL, while in otherembodiments the generated allocation rules are formatted in ExecuteQueries Step 540 to form queries for execution. In some embodiments, aquery is executed for each generated allocation rule. In someembodiments, a query is executed for each generated allocation ruleassociated with a leaf node. For example, in embodiments of HierarchicalData Structure 200, wherein only leaf nodes are used to representBusiness Objects 210A-210W, only the generated allocation rulesassociated with these leaf nodes are needed for allocation.

In an optional Store Query Result Step 550, results of queries executedin Execute Queries Step 540 are stored. Storage may occur on Storage140, Client 120, or another computing device. Typically, the queryresults include those transactions that match the generated allocationrules associated with each of Business Objects 210A-210W. Each queryexecuted in Execute Queries Step 540 serves to select transactions to beallocated to a member of Business Objects 210A-210W. In someembodiments, a transaction can be allocated to more than one member ofBusiness Objects 210A-210W.

In the method illustrated by FIG. 5, transactions are optionallyallocated in separate stages. For example, in one embodiment whereinBusiness Object (Channel Partner) 210H (FIG. 2) is a separate company, abenefit is achieved by allocating transactions to Business Object 210Hand then allowing the separate company to allocate these transactionsamong Business Objects 210M-210S in a separate stage. Thus, eachallocation is optionally viewed as a Transaction Source 130 to aseparate stage of the invention. In one embodiment, the generatedallocation rules used to allocate transactions to Business Object 210Hare not revealed to Business Object 210H. Furthermore, in oneembodiment, only transactions allocated to Business Object 210H arerevealed to Business Object 210H.

FIG. 6 illustrates a method of generating a transaction allocationoutput according to various embodiment of the invention. In a ReceiveQuery Result Step 610 a query result, including selected transactions,is received. This query result is, for example, a query result stored inStore Query Result Step 550 of FIG. 5. The received query result isgenerated using a query based on a hierarchical organizational data(e.g., Hierarchical Data Structure 200). Examples of steps included inthis generation process are illustrated by FIG. 3 and FIG. 4.

In a Parse Transactions Step 620, the selected transactions received inReceive Query Result Step 610 are parsed. During the parsing processtransaction values are identified. In various embodiments, thesetransaction values are, for example, the amount of a sale, the amount ofa sales commission, the amount paid by a customer, the cost of a sale,an inventory allocation, or the like.

In a Sum Transaction Values Step 630 the transaction values identifiedin Parse Transactions Step 620 are summed. In alternative embodiments,alternative or additional mathematical operations are performed on thesetransaction values. In an Include Sum Step 640, the result of themathematical operation, performed in Sum Transactions Values Step 630,are included in the transaction allocation output. In variousembodiments, of the invention, the transaction allocation output is aprinted output, a display output, a digital electronic output, a savedoutput, or the like. For example, in some embodiments, the transactionallocation output is displayed and/or printed using Client 120.

FIG. 7 illustrates an alternative Hierarchical Data Structure, generallydesignated 700, including Root Node 710, Intermediate Nodes 720A-720H,and Leaf Nodes 730A-730N. In Hierarchical Data Structure 700, businessobjects configured to receive transaction allocations are associatedwith at least one of Leaf Nodes 730A-730N. While Root Node 710 andIntermediate Nodes 720A-720H are optionally associated with predefinedrules, generated allocation rules, and/or business objects, thosebusiness objects, with which Root Node 710 and Intermediate Nodes720A-720H are associated, are not necessarily configured to receivetransaction allocations. For example, in the illustrated example,Intermediate Note 720B is associated with an Eastern sales division.Because the Eastern sales division is an organizational business objectand not an individual person it may not be configured to receive sometypes of transaction allocations (e.g. a commission). Root Node 710 andIntermediate Nodes 720A-720H each optionally have at least one daughternode that is a leaf node 730A-730N. This daughter node may be associatedwith a manager of the business object associated with its parent node.For example, Leaf Node 730C, a daughter node of Intermediate Node 720B,may be associated with an Eastern sales division manager.

In the above case, the business object associated with Leaf Node 730Chas a “management” role with respect to Intermediate Node 720B. Inalternative embodiments, this management role is held by a businessobject associated with a node other than an immediate daughter node. Forexample, the business object associated with Leaf Node 730G may have amanagement role with respect to the business objects associated withboth Intermediate Nodes 720D and 720F. The management role with respectto the business object associated with Intermediate Node 720H isillustrated by a Dotted Line 740.

In some embodiments, Root Node 710 and/or specific members ofIntermediate Nodes 720A-720H are associated with a predefined rule butnot with a business object. In some embodiments, Root Node 710 and/orspecific members of Intermediate Nodes 720A-720H are associated with apredefined rule and a business object that is not configured to receivea transaction allocation. This business object may be, for example, aproduct classification. Members of Intermediate Nodes 720A-720H havingdifferent types of associations can be found in a single instance ofHierarchical Data Structure 700.

In embodiments of the invention illustrated by FIG. 7, transactions areallocated by executing queries based on the generated allocation rulesassociated with Leaf Nodes 730A-730N. In these embodiments, it is notnecessary to execute queries based on any generated allocation rulesassociated with Root Node 710 or Intermediate Nodes 720A-720H in orderto allocate transactions. However, as is shown further herein, thesegenerated allocation rules are optionally used for processing oftransactions that are unallocated, under-allocated or over-allocated,using the allocation rules associated with Leaf Nodes 730A-730N alone.

In various embodiments of the invention, a first attempt at allocating aset of transactions is made using generated allocation rules associatedwith leaf nodes, such as Leaf Nodes 730A-730L. This process is similarto that discussed with respect to FIG. 5, except that the queriesexecuted in Execute Queries Step 540 are based on generated allocationrules associated with leaf nodes and those transactions not selected byany query are identified. After Execute Queries Step 540, anytransactions not completely allocated are optionally identified.

In a second attempt at transaction allocation, the identified(unallocated, under-allocated, or over-allocated) transactions arequeried using queries based on generated allocation rules associatedwith root or intermediate nodes, such as Root Node 170 and/orIntermediate Nodes 720A-720H. In some embodiments, the generatedallocation rule associated with Root Node 710 is configured to selectall possible transactions. Thus, in these embodiments, all transactionsnot selected on the first allocation attempt are selected on the secondallocation attempt by at least one query. Results of the secondallocation attempt are used to determine, through additional steps,allocation of the identified transactions to business objects.

FIG. 8 illustrates an example of an allocation method used to allocatetransactions according to various embodiments of the invention. In theseembodiments, several attempts are made to allocate transactions and theadditional attempts are configured to allocate transactions that wereunallocated, under-allocated or over-allocated in a first attempt. Themethod of FIG. 8 includes using Hierarchical Data Structure 700 toallocate transactions that were unallocated, over-allocated orunder-allocated transactions in a previous attempt at allocation. In anAccess Leaf Rules Step 810, generated allocation rules stored in RuleData 150 and associated with Leaf Nodes 730A-730N are accessed usingQuery Engine 170. Leaf Nodes 730A-730N are associated with businessobjects configured to receive transaction allocations. In someembodiments, Access Leaf Rules Step 810 is analogous to Access RulesStep 530 (FIG. 5) except that only generated allocation rules associatedwith business objects configured to receive transaction allocations areaccessed.

In an Execute Leaf Queries Step 820, the generated allocation rulesaccessed in Access Leaf Rules Step 810 are used to execute queries onTransaction Data 155. In some embodiments, Execute Leaf Queries Step 820is analogous to Execute Queries Step 540. As in Execute Queries Step540, the executed queries are typically generated using the accessedallocation rules.

In an Identify Unallocated Transactions Step 830, those transactions notselected in any of the queries executed in Execute Leaf Queries Step 820are identified. These transactions are considered unallocated. In someembodiments, the unallocated transactions are identified by setting anattribute associated with each of the transactions that are allocated.For example, in one embodiment, each of a set of data records includes a“selected” flag and a pointer to an associated transaction. When atransaction is selected by a query this flag is set. In IdentifyUnallocated Transactions Step 830 these records are searched andunallocated transactions are identified.

In an optional Identify Under-allocated Transactions Step 840,transactions that are not completely allocated are identified. Forexample, if a transaction includes a 10% commission on a sale andExecute Leaf Queries Step 820 results in identification of businessobjects configured to receive 8% of the sale, 2% of the sale amount isunallocated. Identify Under-allocated Transactions Step 840 typicallyincludes comparing a value of a transaction available to be allocatedwith a sum of values that could be allocated to business objectsidentified in Execute Leaf Queries Step 820. In various embodiments, the“value” of a transaction is measured in dollars, percentage of anothertransaction, amount of a commodity, amount of time, amount of anotherresource, or the like.

In an optional Identify Over-allocated Transactions Step 850,transactions that are over-allocated are identified. For example, if atransaction includes a 10% commission on a sale and Execute Leaf QueriesStep 820 identifies six business objects, each configured to receive 2%of the sale, then 2% of the sale amount is over-allocated. As inIdentify Under-allocated Transaction Step 840, Identify Over-allocatedTransactions Step 850 typically includes comparing a value of atransaction available to be allocated with a sum of values that could beallocated to business objects identified in Execute Leaf Queries Step820.

In an Allocation Plan Complete Step 860, Allocation Manager 190 is usedto examine the results of Identify Unallocated Transactions Step 830,Identify Under-allocated Transactions Step 840 and/or IdentifyOver-allocated Transactions Step 850. If no transactions have beenidentified as being unallocated, under-allocated or over-allocated inthe allocation plan then the allocation plan is complete and the processcan continue to an optional Allocate Step 865 wherein actual allocationoccurs, as discussed further herein. If there are unallocated,under-allocated or over-allocated transactions then the method continuesto an Access Non-Leaf Rules Step 870.

In Access Non-Leaf Rules Step 870, Allocation Manager 190 is used toaccess generated allocation rules associated with Root Node 710 andIntermediate nodes 720A-720H. In some embodiments, this step isanalogous to Access Leaf Rules Step 810 except that the accessedgenerated allocation rules are not necessarily associated with businessobjects configured to receive transaction allocations.

In an Execute Non-Leaf Queries Step 880, the generated allocation rulesaccessed in Access Non-Leaf Rules Step 870 and Query Engine 170 are usedto execute queries on the transactions identified as being unallocated,under-allocated and/or over-allocated in Steps 830, 840, and 850,respectively. In some embodiments, one of the generated allocation rulesused in Execute Non-Leaf Queries Step 880 is configured to select allpossible transactions, thus ensuring that all transactions will beselected by at least one query in Execute Non-Leaf Queries Step 880.

In an Identify Managing Business Objects Step 890, Allocation Manager190 is used to identify a person, or persons having a role of manuallydetermining the allocation of the transactions selected using each queryin Execute Non-Leaf Queries Step 880. The identification of this personis dependent on the generated allocation rule on which the query wasbased and the business object associated with that generated allocationrule. For example, in some embodiments, several unallocated transactionsare selected using the generated allocation rule associated withIntermediate Node 720D. Intermediate Node 720 is associated with aperson (business object) having a “manager” role and authorized tomanually determine the allocation of these transactions. The personhaving a manager role is optionally also associated with a member ofLeaf Nodes 730A-730N, such as Leaf Node 730G. In some cases, more thanone person having a manager role will be identified for a particulartransaction. Identify Managing Business Objects Step 890 is performedfor each query executed in Execute non-Leaf Queries Step 880.

In a Manual Selection Step 895, the allocation of transactions queriedin Execute Non-Leaf Queries Step 880 are manually determined by thebusiness objects (e.g. person or persons) identified in IdentifyManaging Business Objects Step 890. For example, in some embodiments, aperson associated with Intermediate Node 720H receives a request tomanually determine an allocation plan for unallocated transactions. Shereceives this request because the transactions were selected using thegenerated allocation rule associated with Intermediate Node 720H. Insome of these embodiments, the person associated with Intermediate Node720H is not configured to receive an allocation herself, in otherembodiments she is also associated with a member of Leaf Nodes730A-730N, such as Leaf Nodes 730L or 730M, and thus is configured toreceive allocations. In one embodiment, this person receives a taskassigning her responsibility to manually plan the allocation of thetransactions. The allocation task is optionally facilitated by agraphical user interface showing: a partial allocation, why the personwas chosen, business objects associated with daughter nodes ofIntermediate Node 720H, options (such as an HTML based form) configuredfor manually completing the allocations, allocations to business objectassociated with Leaf Nodes 730A-730N that have already been planned fora particular transaction, and/or the like. In Manual Selection Step 895,the determinations made by the business objects identified in IdentifyManaging Business Objects Step 890 are typically configured to completethe allocation plans of the transactions queried in Execute Non-LeafQueries Step 880.

Following Manual Selection Step 895, the method proceeds to AllocateStep 865 wherein the transactions are allocated to the business objectsspecified in steps 820 and 895.

Several embodiments are specifically illustrated and/or describedherein. However, it will be appreciated that modifications andvariations are covered by the above teachings and within the scope ofthe appended claims without departing from the spirit and intended scopethereof. For example, the various computer systems described herein areoptionally implemented as distributed systems; likewise the location ofspecific data records is optionally varied among a variety ofalternative locations. Communication between various elements of theinvention may occur over the World Wide Web or other computer network.The invention is optionally implemented as an internet application.

The invention is optionally adapted to alternative types of ordered datastructures that allow inheritance between nodes. In addition, in someembodiments, business objects configured to receive an allocation andbusiness objects having management roles need not be classified by thetype of node with which they are associated. In alternative embodiments,alternative methods of identification are used. For example, in oneembodiment, a role attribute may be used to distinguish business objectsconfigured to receive allocations and/or to have a manager role. In thisembodiment, the role attribute is used to determine which rules areaccessed in steps 810 and 870. In some embodiments, a generatedallocation rule can be empty (e.g., no allocation rule is inherited orpredefined) and, in some embodiments, the systems and methods of theinvention are used to update existing allocation rules. In someembodiments, a generated allocation rule is determined by traversinghierarchical Data Structure 200 from a leaf node, to an intermediatenode, and then to the root node. In these embodiments, the generatedallocation rule is generated by collecting predefined rules associatedwith traversed nodes. Embodiments of the invention include computer codestored on a computer readable medium and configured to execute methodsof the invention.

In this application “allocation rules” are meant to include both rulesused to select a business object to receive an allocation resulting froma transaction and rules used to calculate the amount of the allocation.In some embodiments, an allocation of all or part of a transaction to abusiness object is treated as a new transaction. For example, thepayment of a commission, once determined, is optionally managed as a newtransaction.

1. A transaction filtering system for allocating transactions among aplurality of business objects, the system comprising: storage configuredto store generated allocation rules and to store transaction dataassociated with a plurality of transactions, each generated allocationrule being associated with at least one of the plurality of businessobjects, each generated allocation rule being generated by combining afirst predefined rule of a node of a hierarchical data structure with asecond predefined rule inherited from a parent node, the firstpredefined rule characterizing a member of the at least one of theplurality of business objects; a query engine configured to query thetransaction data using the generated allocation rules; and an allocationmanager configured to make one or more attempts to allocate a member ofthe plurality of transactions among the plurality of business objects,wherein each generated allocation rule determines if a business objectis entitled to an allocation from a particular transaction.
 2. Thetransaction filtering system of claim 1, wherein a member of theplurality of transactions is a sale and the query engine is configuredto determine commission allocation.
 3. The transaction filtering systemof claim 1, wherein a member of the plurality of transactions is apurchase and the query engine is configured to determine costallocation.
 4. The transaction filtering system of claim 1, wherein amember of the plurality of transactions is unallocated after a firstattempt at allocation.
 5. The transaction filtering system of claim 1,wherein a member of the plurality of transactions is under-allocatedafter a first attempt at allocation.
 6. The transaction filtering systemof claim 1, wherein a member of the plurality of transactions isover-allocated after a first attempt at allocation.
 7. The transactionfiltering system of claim 1, wherein a second attempt at allocating themember of the plurality of transactions includes identifying a businessobject configured to manually determine the allocation.
 8. A computingsystem for hierarchical transaction filtering, the computing systemcomprising: storage configured to store a hierarchical data structure, afirst generated allocation rule associated with a first business object,a second generated allocation rule associated with a second businessobject, and transaction data; an allocation manager configured to trackallocations of transactions represented by the transaction data andtrack whether the business objects are entitled to an allocation from aparticular transaction; and a query engine configured to execute a firstquery on the transaction data using the first generated allocation ruleand, responsive to the first query, to execute a second query on thetransaction data using the second generated allocation rule, wherein thefirst generated allocation rule includes a predefined rule inheritedfrom a parent node.
 9. The computing system of claim 8, wherein thehierarchical data structure is configured to represent relationshipsbetween business objects in a sales organization.
 10. The computingsystem of claim 8, wherein the first generated allocation rule isproduced by traversing the hierarchical data structure.
 11. Thecomputing system of claim 8, wherein the second query is configured toidentify a business object having a management role with respect to anode of the hierarchical data structure.
 12. The computing system ofclaim 8, further including a transaction source configured to generatethe transaction data.
 13. A computer program product embedded in anon-transitory computer readable medium for allocating transactionsamong a plurality of business objects, the computer program productincluding instructions that, when executed by a processor, cause theprocessor to: store generated allocation rules and transaction dataassociated with a plurality of transactions, each generated allocationrule being associated with at least one of the plurality of businessobjects, each generated allocation rule being generated by combining afirst predefined rule of a node of a hierarchical data structure with asecond predefined rule inherited from a parent node, the firstpredefined rule characterizing a member of the at least one of theplurality of business objects; query the transaction data using thegenerated allocation rules; and make at least one attempt to allocate amember of the plurality of transactions among the plurality of businessobjects, wherein each generated allocation rule determines if a businessobject is entitled to an allocation from a particular transaction. 14.The computer program product of claim 13, wherein a member of theplurality of transactions is a sale and the query step includesdetermining commission allocation.
 15. The computer program product ofclaim 13, wherein a member of the plurality of transactions is apurchase and the query is configured to determine cost allocation. 16.The computer program product of claim 13, wherein a member of theplurality of transactions is unallocated after a first attempt atallocation.
 17. The computer program product of claim 13, wherein amember of the plurality of transactions is under-allocated after a firstattempt at allocation.
 18. The computer program product of claim 13,wherein a member of the plurality of transactions is over-allocatedafter a first attempt at allocation.
 19. The computer program product ofclaim 13, wherein a second attempt at allocating the member of theplurality of transactions includes identifying a business objectconfigured to manually determine the allocation.
 20. A computer programproduct embedded in a computer readable medium for hierarchicaltransaction filtering, the computer program product includinginstructions that, when executed by a processor, cause the processor to:store a hierarchical data structure, a first generated allocation ruleassociated with a first business object, a second generated allocationrule associated with a second business object, and transaction data;track allocations of transactions represented by the transaction dataand track whether the business objects are entitled to an allocationfrom a particular transaction; and execute a first query on thetransaction data using the first generated allocation rule and,responsive to the first query, execute a second query on the transactiondata using the second generated allocation rule, wherein the firstgenerated allocation rule includes a predefined rule inherited from aparent node.
 21. The computer program product of claim 20, wherein thehierarchical data structure is configured to represent relationshipsbetween business objects in a sales organization.
 22. The computerprogram product of claim 20, wherein the first generated allocation ruleis produced by traversing the hierarchical data structure.
 23. Thecomputer program product of claim 20, wherein the second query isconfigured to identify a business object having a management role withrespect to a node of the hierarchical data structure.
 24. The computerprogram product of claim 20, further including a transaction sourceconfigured to generate the transaction data.